Earl Duque
This week, we are continuing the San Diego Release Season content with new features in Integration Hub, an apt follow-up to last week’s Flow Designer topics. Yes, that’s Integration Hub, renamed from IntegrationHub. Why? Well, ServiceNow is moving forward with new features that will have similar naming and who doesn’t like a little bit of naming convention in the morning?
So, just like our comic books fans out there. For Spider-man, we “respect the hyphen!
San Diego! The Developer Program content pipeline is getting spruced up and ready for the San Diego release for ServiceNow! From February 7, 2022 to April 15, 2022 we will be releasing content every week for our very own “San Diego” content season.
Every week during this season we will release a blog post, an episode of Creator Toolbox, and an episode of Live Coding Happy Hour. We will cover the Next Experience, Flow Designer, Integration Hub, Studio, Platform, App Engine Studio, Mobile, and a new product yet to be announced!
The 2022 application has closed. The developer mentorship program will re-launch as the Community Mentorship Program and redesigned as a cohort model with expanded inclusion of non-developer roles. You can fill out an interest form here to be the first to know when the new program is expected to launch.
Who is this for? This program is open to anyone who builds, creates, or develops on the Now Platform. If you’d like to mentor someone, or gain great insights by being mentored, we’d love to have you.
Soon, the 2022 Developer MVP cohort will be revealed but before we get there, we asked our 2021 Developer MVPs to share some New Year wisdom.
Advice Earl: Your biggest advocate should always be you**: maintain that portfolio, speak well of yourself, make the best choices for you. A company is always watching out for itself, you should always be watching out for yourself/your family. Chuck: Find a personal project to digitize/automate some project of your own.
October is behind us and our most successful ServiceNow Hacktoberfest is in the books! Here are the final numbers for 2021:
452 Pull requests 22x Increase from last year 90 Contributors 119 Pull requests reviewed by volunteers niammcash paigesndev smartcarleen mgopw 292 forks across all repos Show us your stickers and shirts! When you receive your Hacktoberfest swag from DigitalOcean, be sure to post on social with the hashtag #ServiceNowDev so everyone can see your hard-earned loot!
Happy Diwali!!
As we enter the US Holiday Season we want to let our awesome developers know we wish them a Happy Diwali. May your life be as colorful, shimmering, and magical as the lights of Diwali!
We are past the half-way point on Hacktoberfest and wanted to highlight the amazing progress so far! If you haven’t participated yet, you still have time! Check out our Hacktoberfest 2021 post to get started.
Remember to claim your prize! If you already have participated and have made your four qualifying pull requests, don’t forget to go to DigitalOcean to claim your rewards!
Pull Requests Hacktoberfest completion is measured in “Pull requests” approved and merged so let’s take a look at that first:
It’s that time of year again! Every year we encourage ServiceNow Developers to participate in DigitalOcean’s Hacktoberfest event by contributing to a ServiceNow project or repository.
Why participate? The more the community is equipped, the more that community can contribute. The more you get used to source-controlled projects, the more you can contribute to any number of open-source projects. You get a free t-shirt (the t-shirt also comes with bragging rights)!
In this post, we will provide a walk through on how to create your first and basic playbook in ServiceNow. If you saw Live Coding Happy Hour on August 19, 2021 (part 1) or September 2, 2021 (part 2), this post will go through the same material.
Playbooks provide step-by-step guidance for resolving processes and enable agents to easily manage the lifecycle of cases by guiding them through sequences of tasks.
Let’s keep the Rome Release feature highlights going!
Instance Scan, introduced in Quebec, was a great addition to the platform that allowed us to check our instances for issues or deviations from best practices. It is a great tool to use to maintain a high level of standard while doing development, performing releases, and during upgrades.
Before Rome Instance Scanning was either manual (you executed a scan suite yourself) or scheduled.
